The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Mar 13, 2026 2:31am

PR Summary

Medium Risk
Adds a new persisted resources JSONB column on copilot_chats plus new API/mutation paths that update it, and wires tool execution to emit and store resources; mistakes could lead to incorrect resource lists or ordering in tasks. Changes touch both orchestrator SSE flow and client state updates, increasing integration risk.

Overview
Persists “open resources” on copilot tasks and makes them user-editable. Chats now store a resources array in copilot_chats and /api/copilot/chat includes it in GET responses.

Adds a dedicated /api/copilot/chat/resources endpoint to add/remove/reorder resources (with basic validation + title de-duplication), plus new React Query mutations to call it.

Updates the task UI to support adding resources via a + dropdown, closing tabs, and drag-and-drop reordering, and refactors resource rendering via a new resource-registry + ResourceActions.

Integrates resource persistence into execution: tool results can yield resources (including via VFS read), the orchestrator persists them and emits a new resource_added SSE event, and the client updates local state + invalidates relevant queries on receipt.

^{Written by Cursor Bugbot for commit 847c899. This will update automatically on new commits. Configure here.}

Greptile Summary

This PR replaces the previous heuristic client-side resource extraction (parsing SSE payloads) with authoritative server-side persistence: tool results now emit resource_added SSE events and write to a new resources JSONB column on copilotChats. Users can also manually add, remove, and reorder resources via a new REST API (/api/copilot/chat/resources) and a redesigned ResourceTabs with drag-and-drop, close buttons, and an AddResourceDropdown.

Key observations:

• The new persistChatResources utility omits updatedAt when writing to the DB, inconsistent with the three API route handlers that all set it explicitly.
• The VALID_RESOURCE_TYPES.has(resource.type) guard in the POST route is dead code — Zod's z.enum(...) already guarantees the value before it is reached.
• renderActions is defined in ResourceTypeConfig (and implemented for workflow/knowledgebase) but is never called from MothershipView or any other consumer — both the interface field and its implementations (WorkflowActions, KnowledgeBaseActions) are unreachable.
• Auto-scroll during tab drag-and-drop duplicates requestAnimationFrame logic across the tab onDragOver handler and the container onDragOver; due to event bubbling, the container handler fires second and cancels the RAF started by the tab handler, which may prevent scrolling from working correctly in edge zones.
• The onKeyDown close button handler casts React.KeyboardEvent to React.MouseEvent via as unknown as, which is type-unsafe.
• A database migration file for the new resources column is not included in this PR.

Confidence Score: 3/5

• This WIP PR has several correctness issues (missing updatedAt, broken auto-scroll RAF, unreachable code paths) and a missing DB migration that should be resolved before merging.
• The core data flow — server-side extraction → SSE event → client state → DB persistence — is architecturally sound and well-tested with optimistic updates. However, the missing updatedAt write, the dead renderActions registry code that duplicates live components, the RAF clobbering bug in drag-and-drop, and the absence of a DB migration each represent production risks that reduce confidence below a "ready to merge" threshold.
• apps/sim/lib/copilot/resources.ts (missing updatedAt), apps/sim/app/workspace/[workspaceId]/home/components/mothership-view/components/resource-tabs/resource-tabs.tsx (RAF/drag-and-drop), apps/sim/app/workspace/[workspaceId]/home/components/mothership-view/components/resource-registry.tsx (dead renderActions), packages/db/schema.ts (migration needed)

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Client as Browser (useChat)
    participant SSE as SSE Stream
    participant ToolExec as tool-execution.ts
    participant DB as Database (copilotChats)
    participant API as /api/copilot/chat/resources

    Client->>SSE: sendMessage()
    SSE->>ToolExec: executeToolAndReport()
    ToolExec->>ToolExec: extractResourcesFromToolResult()
    ToolExec-->>DB: persistChatResources() [fire-and-forget]
    ToolExec-->>SSE: emit resource_added event
    SSE-->>Client: { type: 'resource_added', resource }
    Client->>Client: addResource() → setResources()

    Note over Client,DB: User manually adds/removes/reorders

    Client->>API: POST /resources (add)
    API->>DB: UPDATE copilotChats SET resources = merged
    API-->>Client: { success, resources }

    Client->>API: DELETE /resources (remove)
    API->>DB: UPDATE copilotChats SET resources = filtered
    API-->>Client: { success, resources }

    Client->>API: PATCH /resources (reorder)
    API->>DB: UPDATE copilotChats SET resources = newOrder
    API-->>Client: { success, resources }

    Note over Client,DB: On page reload
    Client->>API: GET /api/copilot/chat?chatId=...
    API->>DB: SELECT resources FROM copilotChats
    DB-->>API: resources[]
    API-->>Client: chatHistory.resources
    Client->>Client: setResources(chatHistory.resources)

_{Last reviewed commit: 544af06}